Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1499

reference: 713-tree-1
name: 1499
tree-preservation-order: undefined
713-tpo-1
uprn
address-text
point: POINT (-0.971443 50.866491)
geometry: MULTIPOLYGON (((-0.971372 50.866484,-0.971375 50.866498,-0.971385 50.866510,-0.971401 50.866521,-0.971420 50.866527,-0.971442 50.866529,-0.971464 50.866527,-0.971484 50.866521,-0.971500 50.866511,-0.971511 50.866499,-0.971514 50.866485,-0.971511 50.866471,-0.971501 50.866459,-0.971486 50.866449,-0.971466 50.866442,-0.971444 50.866440,-0.971422 50.866442,-0.971402 50.866448,-0.971386 50.866458,-0.971376 50.866470,-0.971372 50.866484)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL